home *** CD-ROM | disk | FTP | other *** search
- Path: phoenix.rhein.de!yaps!arno
- From: arno@yaps.rhein.de (Arno Eigenwillig)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: WBStartup - Help!
- Message-ID: <lZyYx*dif@yaps.rhein.de>
- Date: Thu, 18 Jan 1996 15:59:17 +0100
- References: <vreeland-1601961903260001@192.0.2.1>
- Organization: Yet Another Private Site in Meckenheim, Germany
- X-Copyright: This article may not be distributed on a CD-ROM
- or in printed form without prior written consent of the author.
- X-Newsreader: Arn V 1.04
-
- In article <vreeland-1601961903260001@192.0.2.1>, Robert W. Vreeland Jr. writes:
-
- > The new process never ends up with correct command paths setup.
-
- This is because programs launched a la Workbench never have a command
- path! The command path is inherited only by CLIs from the invoking CLI
- (or Workbench, if started by icon) and stored via the CommandLineIn-
- terface structure which is an extension to the Process structure and
- not available for Workbench programs.
-
- > The assigns ARE setup
-
- This is because they are handled completely different. They are stored
- centrally as nodes in dos.library's DosList, not per process.
-
- > Now I've compared both the
- > WBStartup message and the Process structure that my code ends up creating
-
- I take that to mean: creates through system calls. Allocating a
- process structure manually is unwise.
-
- PS: You may want to use the freely available WBStart-Handler by Stefan
- Becker instead of reinventing the wheel...
-
- -- __
- __/// Arno Eigenwillig /\ <arno@yaps.rhein.de> \/ PGP key available.
- \XX/ V+49-2225-5870 /\ <Arnooo @ #amigager> \/ MIME 8bit welcome.
-